Log File Size - Best Practice (SQL Server 2017) : rSQLServer

A transaction log file that is larger than the data file can indicate that: Transaction log backups are not being performed (or are not being ...

There are a number of reasons a log file can fill to extreme sizes. The most common one by far is that the database is in full recovery model.

A Full backup daily at 4:00AM · Transaction Log backup every 2 hours · Backup Cleanups to remove anything older than 1 week · Rebuild index weekly ...

To enlarge the log file, use the MODIFY FILE clause of the ALTER DATABASE statement, specifying the SIZE and MAXSIZE syntax. For more ... Shrink a File · ALTER DATABASE File and... · Sys.dm_db_log_space_usage

The log file NEVER gets physically smaller, unless you manually shrink it. A log backup set the data inside as logically available for reuse.

I did a shrink on the log file and its still 2 and a half gigs. Nothing I do seems to shrink the file in size. Is there anyway to fix the problem?

Increase the Log File Size: You can increase the log file size. The maximum size for a log file is two terabytes. Enable Autogrowth: Autogrowth ...

Microsoft SQL Server Database log files can grow large causing your database to go offline and be unavailable if the Transaction Log drive ...

If you right click on the database in object explorer > tasks > shrink you can view in the gui how much space is unused in your log file.

When log files keep growing and appear to be too big some might suggest switching to Simple recovery, shrinking the log file, and switching back to Full ...